Optical Bandwidth Manager

ABSTRACT

A computer-readable medium storing instructions that, when executed by one or more processors, cause the one or more processors to: receive a setup request for an optical path between a source entity of network entities in an optical network and a destination entity of the network entities, identify a first channel and a second channel having one or more contiguous first span with an allocation status of available and being configurable to provide the optical path between the source entity and the destination entity; analyze network configuration data indicative of the first channel and the second channel with a fragmentation heuristic to generate an allocation recommendation recommending the first channel to be allocated to the optical path; and provide the allocation recommendation identifying the first channel for allocation to the optical path.

BACKGROUND

An Optical Transport Network (OTN) is comprised of a plurality of switchnodes linked together to form a network. The OTN includes an electroniclayer and an optical layer. The electronic layer and the optical layereach contain multiple sub-layers. The optical layer provides opticalconnections, also referred to as optical channels or lightpaths, toother layers, such as the electronic layer. The optical layer performsmultiple functions, such as monitoring network performance, multiplexingwavelengths, and switching and routing wavelengths. In general, the OTNis a combination of the benefits of SONET/SDH technology and densewavelength-division multiplexing (DWDM) technology (optics). OTNstructure, architecture, and modeling are further described in theInternational Telecommunication Union recommendations, including ITU-TG.709, ITU-T G.872, and ITU-T G.805, which are well known in the art.

The construction and operation of switch nodes (also referred to as“nodes”) in the OTN is well known in the art. In general, the nodes ofan OTN are generally provided with a control module, input interface(s)and output interface(s). The control modules of the nodes in the OTNfunction together to aid in the control and management of the OTN. Thecontrol modules can run a variety of protocols for conducting thecontrol and management of the OTN. One prominent protocol is referred toin the art as Generalized Multiprotocol Label Switching (GMPLS).

Generalized Multiprotocol Label Switching (GMPLS) is a type of protocolwhich extends multiprotocol label switching (MLS) to encompass networkschemes based upon time-division multiplexing (e.g. SONET/SDH, PDH,G.709), wavelength multiplexing, and spatial switching (e.g. incomingport or fiber to outgoing port or fiber). Multiplexing is when two ormore signals or bit streams are transferred over a common channel.Wave-division multiplexing is a type of multiplexing in which two ormore optical carrier signals are multiplexed onto a single optical fiberby using different wavelengths (that is, colors) of laser light.

RSVP and RSVP-TE signaling protocols may be used with GMPLS. To set up aconnection in an Optical Transport Network, nodes in the OpticalTransport Network exchange messages with other nodes in the OpticalTransport Network using RSVP or RSVP-TE signaling protocols. Resourcesrequired for the connection are reserved and switches inside the networkare set. Information sent by signaling protocols are often in atype-length-value (TLV) format. The same protocols may also be used totake down connections in the Optical Transport Network when theconnections are no longer needed.

OSPF and OSPF-TE routing and topology management protocols may also beused with GMPLS. Under OSPF protocols, typically each node in an OpticalTransport Network maintains a database of the network topology and thecurrent set of resources available, as well as the resources used tosupport traffic. In the event of any changes in the network, or simplyperiodically, the node floods the updated topology information to allthe Optical Transport Network nodes. The nodes use the databaseinformation to chart routes through the Optical Transport Network.

Traffic Engineering (TE) is a technology that is concerned withperformance optimization of operational networks, such as OTNs. Ingeneral, Traffic Engineering includes a set of applications, mechanisms,tools, and scientific principles that allow for measuring, modeling,characterizing and control of user data traffic in order to achievespecific performance objectives.

Current Traffic Engineering practices have been utilized to increase thedata rates in networks. However, future information transport systemsare expected to support service upgrades to data rates of one terabyteper second (Tbps) and beyond. To accommodate such high rates intransport network architectures, multi-carrier Super-Channels coupledwith advanced multi-level modulation formats and flexible channelspectrum bandwidth allocation schemes may be utilized. In this instance,spectrum allocated to particular Super-Channels is very flexible. SuperChannels carry data using optical carriers which are bands within theoptical spectrum. In other words, the Super Channels can be accommodatedby combining several optical carriers together. In these types ofnetworks, a routing and spectrum assignment (RSA) algorithm may be usedto setup the Super Channels. The RSA algorithm considers the spectrumcontinuity and optical carrier consecutiveness constraints whileassigning a spectrum path (SP) to any incoming connection. The spectrumcontinuity constraint requires continuous availability of opticalcarriers along an optical route (if no frequency converter is provided).The optical carrier consecutiveness constraint requires that the opticalcarriers assigned to any Super Channel should be consecutive in spectrumdomain. Due to the additional constraints, the RSA problem in opticalnetworks is even more challenging. The dynamic RSA problem can also bechallenging due to the random traffic arrival/departure and thefluctuation of the traffic demands over time.

In optical networks with dynamic traffic, the frequent set-up and teardown of optical routes can lead to significant fragmentation of spectralresources. Due to the spectrum continuity and optical carrierconsecutiveness constraints, several spectrum slots in betweenconnections remain unused thereby reducing the amount of data that canbe transported within the optical network. In particular, these spectralfragments of unused spectrum fragments may be small, scattered and maynot be enough to establish new optical routes because of aforementionedconstraints in optical networks. As a result, the spectral fragmentsincrease the maximum sub-carrier index (MSI) in each fiber or decreasethe probability of finding sufficient contiguous sub-carriers for newoptical routes. Requests for new optical routes are then forced eitherto utilize more spectrum in the fiber or are blocked even thoughsufficient spectrum are available. Hence, the spectral fragments producea significant amount of waste of the expensive spectral resources whichmay lower spectral usage and increase blocking.

Conventional techniques for solving this problem include spectraldefragmentation algorithms that reconfigure existing connections withthe goal of consolidating the spectrum allocation. The scattered andfragmented spectrum slots can be consolidated by either shifting theexisting optical carrier allocation between one node pair to a differentgroup of optical carriers, assigning a new route to an existingconnection, or both while maintaining the optical carrierconsecutiveness and spectrum consecutiveness constraints. Networkadministrators can perform the spectrum defragmentation on a periodicmanner to consolidate spectrum or on demand when the links' opticalcarrier index increases beyond a threshold (indicating the potentialblocking of future connection requests).

There is a need to reduce fragmentation in optical networks to enhancespectral usage and the amount of data traffic transported by the opticalnetwork. The present disclosure addresses this need with methodologiesand systems that reduces the amount of fragmentation by generatingallocation recommendations that, if followed by a network administrator,reduces the fragmentation of the optical network when the networkadministrator is processing requests for new optical routes.

SUMMARY

In one version, the present disclosure describes a computer-readablemedium that stores one or more instructions that, when executed by oneor more processors, cause the one or more processors to provide via atleast one of an output component and a communication interface, a userinterface that displays a representation of an optical network having atleast three network entities and at least two optical links configuredto carry optical signals in a first channel and a second channel acrossat least a first span and a second span between the at least threenetwork entities. The first channel has a first allocation status ofavailable on the first span, and a second allocation status of at leastone of unavailable, assigned and blocked on the second span. The secondchannel has a third allocation status of available on the first span anda fourth allocation status of available on the second span. Theinstructions also cause the one or more processors to receive, via aninput component, user input regarding a setup request for an opticalpath between a source entity of the network entities and a destinationentity of the network entities, the optical path encompassing the firstspan and mutually exclusive to the second span. The instructions causethe one or more processors to provide, via the at least one of theoutput component and the communication interface, a visualrepresentation within the user interface of an allocation recommendationidentifying the first channel of the first span, based on the user inputregarding the setup request, the first allocation status, the secondallocation status and the third allocation status.

In another version, the present disclosure describes a computer-readablemedium storing instructions that, when executed by one or moreprocessors, cause the one or more processors to: receive, via at leastone of an input component and a communication interface, a setup requestfor an optical path between a source entity of network entities in anoptical network and a destination entity of the network entities;identify a first channel and a second channel having one or morecontiguous first span with an allocation status of available and beingconfigurable to provide the optical path between the source entity andthe destination entity; analyze network configuration data indicative ofthe first channel and the second channel with a fragmentation heuristicto generate an allocation recommendation recommending the first channelto be allocated to the optical path; and provide, via an outputcomponent, the allocation recommendation identifying the first channelfor allocation to the optical path.

In yet another version, the present disclosure describes a method inwhich at least one of an input component and a communication interfacereceives a setup request for an optical path between a source entity ofnetwork entities in an optical network and a destination entity of thenetwork entities. A first super-channel and a second super-channel areidentified. The first super-channel and the second super-channel haveone or more contiguous first span with an allocation status of availableand are configurable to provide the optical path between the sourceentity and the destination entity. Network configuration data indicativeof the first super-channel and the second super-channel is analyzed witha fragmentation heuristic to generate an allocation recommendationrecommending the first super-channel to be allocated to the opticalpath. An output component provides the allocation recommendationidentifying the first channel for allocation to the optical path, andsignals are passed via the communication interface to allocate the firstsuper-channel to the optical path.

BRIEF DESCRIPTION OF DRAWINGS

FIGS. 1A-1C are diagrams of an overview of an example implementationdescribed herein;

FIG. 2A is a diagram of an example environment in which systems and/ormethods described herein may be implemented;

FIG. 2B is a diagram of example devices of an optical network that maybe monitored and/or configured according to implementations describedherein;

FIG. 2C is a diagram of example super-channels that may be monitoredand/or configured according to implementations described herein;

FIG. 3 is a diagram of example components of one or more devices and/orsystems of FIG. 2A and/or FIG. 2B;

FIG. 4 is a diagram of example functional components of one or moredevices of FIG. 2A and/or FIG. 2B;

FIG. 5 is a diagram of example super-channels types that may be used toallocate optical network capacity;

FIG. 6 is a diagram of an example user interface for providing opticalnetwork configuration data;

FIG. 7 is a diagram of an example user interface that may aid a user inselecting a super-channel type for allocating optical network capacity;

FIG. 8 is a diagram of an example user interface that may aid a user inselecting a super-channel for allocating optical network capacity;

FIG. 9 is a diagram of another example user interface that may aid auser in selecting a super-channel for allocating optical networkcapacity;

FIG. 10 is a diagram of an example user interface that may aid a user inselecting spectral slices for allocating optical network capacity;

FIG. 11 is a diagram of an example user interface that may aid a user inselecting an Optical Carrier Group for allocating optical networkcapacity;

FIG. 12 is a diagram of an example user interface that may aid a user inallocating optical network capacity;

FIG. 13 is a diagram of an example process for receiving and storingnetwork configuration information; and

FIG. 14 is a diagram of an example process for allocating bandwidth onnetwork entities via a user interface.

FIG. 15 is a diagram of an example process for generating an allocationrecommendation to allocate a channel to an optical route withoutincreasing fragmentation of the optical network.

FIG. 16 is a diagram of an exemplary graphical user interface forobtaining the allocation recommendation.

FIG. 17 is a diagram of an example user interface showing an allocationrecommendation that may aid a user in selecting an Optical Carrier Groupfor allocating optical network capacity without increasing fragmentationof the optical network.

FIG. 18 is a diagram of an example user interface that may be populatedwith data indicative of a selected channel to assist a user inallocating optical network capacity.

DETAILED DESCRIPTION

The following detailed description of example embodiments refers to theaccompanying drawings. The same reference numbers in different drawingsmay identify the same or similar elements.

As used herein, a “route” and/or an “optical route” may correspond to anoptical path and/or an optical lightpath. For example, an optical routemay specify a path along which light is carried between two or morenetwork entities.

Users of optical networks often need to allocate network capacity (e.g.,bandwidth) in order to transmit data. Allocating optical networkcapacity can be difficult, and may require technicians to directlyadjust the hardware associated with network entities (e.g., nodes).Implementations described herein assist a user in remotely allocatingnetwork capacity on optical network entities, thus making opticalnetwork capacity allocation easier and more efficient.

As discussed above, in optical networks with dynamic traffic, thefrequent set-up and tear down of optical routes can lead to significantfragmentation of spectral resources. Due to the spectrum continuity andoptical carrier consecutiveness constraints, several spectrum slots inbetween connections remain unused thereby reducing the amount of datathat can be transported within the optical network. The presentdisclosure addresses this need with methodologies and systems thatreduces the amount of fragmentation by generating allocationrecommendations that, if followed by a network administrator, reducesthe fragmentation of the optical network when the network administratoris processing requests for new optical routes. To setup a new opticalroutes, a setup request for an optical route between a source entity ofnetwork entities in an optical network and a destination entity of thenetwork entities is received by a component of a network administratorsystem. The network administrator system identifies a first channel anda second channel having one or more contiguous first span with anallocation status of available and being configurable to provide theoptical route between the source entity and the destination entity. Thenetwork administrator system analyzes network configuration dataindicative of the first channel and the second channel with afragmentation heuristic to generate an allocation recommendationrecommending the first channel to be allocated to the optical path.Then, the network administrator system provides the allocationrecommendation identifying the first channel for allocation to theoptical route to a user.

FIGS. 1A through 1C are diagrams of an overview 100 of an implementationdescribed herein. As illustrated in FIG. 1A, a user 102 interacting witha user device 104 may request a graphical user interface 106 (shown inFIG. 1B) (“GUI”) to be displayed on a screen 107 of the user device 104.The GUI 106 may show network configuration information (e.g., abandwidth allocation) from a network administrator system 108. Thenetwork administrator system 108 may request the network configurationinformation from one or more network entities 120-1, 120-2 and 120-3 inan optical network 124. The network administrator system 108 may receivethe requested information from the network entities 120-1, 120-2 and120-3, and may provide the requested GUI 106 to the user device 104.

As illustrated in FIG. 1B, the user 102 may request information to bedisplayed in the GUI 106 by selecting one or more network entities120-1, 120-2, 120-3 and/or optical routes 130-1, 130-2, 130-3, 130-4,130-5 and 130-6 to display. The user 102 may then select a super-channeltype to display optical routes 130-1, 130-2, 130-3, 130-4, 130-5 and130-6 conforming to the super-channel type on the GUI 106. For example,the user 106 may select a super-channel type (e.g., super-channel type3, as illustrated). A super-channel may include multiple channelsmultiplexed together using wavelength-division multiplexing in order toincrease transmission capacity. Various quantities of channels may becombined into super-channels using various modulation formats to createdifferent super-channel types having different characteristics. The GUI106 may display network configuration information associated with theselected network entities 120-1, 120-2 and 120-3 and the selectedsuper-channel type. For example, the GUI 106 may display an indicationof whether a super-channel of the selected type has an allocation statusof available, assigned, used, and/or blocked, as illustrated. The user102 may select an available super-channel in order to allocate bandwidthto the selected super-channel.

As illustrated in FIG. 1C, the requested bandwidth allocation may bereceived by the network administrator system 108. The networkadministrator system 108 may provide the requested bandwidth allocationto network entities 120-1, 120-2 and/or 120-3 associated with theselected super-channel. The network entities 120-1, 120-2 and/or 120-3may allocate the requested bandwidth, and may provide a verification ofthe bandwidth allocation to the network administrator system 108. Thenetwork administrator system 108 may update the GUI 106 on the userdevice 104 to indicate that the requested bandwidth has been allocated.

FIG. 2A is a diagram of an example environment 200 in which systemsand/or methods described herein may be implemented. Environment 200 mayinclude a network planning system 210 (“NPS 210”), a networkadministrator system 220 (“NA 220”), a user device 230, and an opticalnetwork 240 that includes one or more network entities 250-1 through250-N (N≧1) (hereinafter referred to individually as “NE 250” andcollectively as “NEs 250”).

The number of devices and/or networks illustrated in FIGS. 1A and 2A isprovided for explanatory purposes. In practice, there may be additionaldevices and/or networks, fewer devices and/or networks, differentdevices and/or networks, or differently arranged devices and/or networksthan are shown in FIGS. 1A and 2A. Furthermore, two or more of thedevices illustrated in FIG. 2A may be implemented within a singledevice, or a single device illustrated in FIG. 2A may be implemented asmultiple, distributed devices. Additionally, or alternatively, one ormore of the devices of environment 200 may perform one or more functionsdescribed as being performed by another one or more of the devices ofenvironment 200. Devices of environment 200 may interconnect via wiredconnections, wireless connections, or a combination of wired andwireless connections.

NPS 210 may include one or more devices that gather, process, search,store, and/or provide information in a manner described herein. NPS 210may assist a user in modeling and/or planning an optical network, suchas optical network 240. For example, NPS 210 may assist in modelingand/or planning an optical network configuration, which may include aquantity, location, capacity, and/or configuration of NEs 250,characteristics and/or configurations (e.g., capacity) of super-channelsbetween NEs 250, traffic demands of NEs 250 and/or super-channelsbetween NEs 250, and/or any other network configuration informationassociated with optical network 240 (e.g., optical deviceconfigurations, digital device configurations, etc.). NPS 210 mayprovide information associated with the optical network configuration toNA 220 so that a user may view, change, and/or interact with networkconfiguration information.

NA 220 may include one or more devices that gather, process, search,store, and/or provide information in a manner described herein. NA 220may receive network configuration information. For example, NA 220 mayreceive network configuration information from NPS 210, user device 230,optical network 240, and/or NEs 250. NA 220 may provide the networkconfiguration information to another device, such as user device 230, sothat the user 102 may interact with the network configurationinformation. NA 220 may receive information associated with changes tothe network configuration from another device (e.g., user device 230),such as a desired bandwidth and/or super-channel allocation between NEs250. NA 220 may provide information associated with the networkconfiguration changes to optical network 240 and/or NEs 250 in order toallocate network bandwidth and/or super-channels based on the desiredallocation. NA 220 may provide information associated with the networkconfiguration changes to another device, such as user device 230, sothat the user 102 may interact with the changed network configurationinformation.

User device 230 may include one or more devices that gather, process,search, store, and/or provide information in a manner described herein.In some implementations, user device 230 may include a computer (e.g., adesktop computer, a laptop computer, a tablet computer, etc.), aradiotelephone, a personal communications system (“PCS”) terminal (e.g.,that may combine a cellular telephone with data processing and datacommunications capabilities), a personal digital assistant (“PDA”)(e.g., that may include a radiotelephone, a pager, Internet/intranetaccess, etc.), a smart phone, and/or any other type of computationand/or communication device. User device 230 may provide information toand/or receive information from other devices, such as NA 220. Forexample, user device 230 may receive network configuration informationfrom NA 220, and may send information associated with networkconfiguration changes to NA 220.

Optical network 240 may include any type of network that uses light as atransmission medium. For example, optical network 240 may include afiber-optic based network, an optical transport network, alight-emitting diode network, a laser diode network, an infrarednetwork, and/or a combination of these or other types of opticalnetworks.

NEs 250 may include one or more devices that gather, process, store,and/or provide information in a manner described herein. For example,NEs 250 may include one or more optical data processing and/or traffictransfer devices, such as an optical node, an optical add-dropmultiplexer (“OADM”), a reconfigurable optical add-drop multiplexer(“ROADM”), an optical multiplexer, an optical demultiplexer, an opticaltransmitter, and optical receiver, an optical transceiver, a photonicintegrated circuit, an integrated optical circuit, a computer, a server,a router, a bridge, a gateway, a modem, a firewall, a switch, a networkinterface card, a hub, and/or any type of device capable of processingand/or transferring optical traffic. In some implementations, NEs 250may include OADMs and/or ROADMs capable being configured to add, drop,multiplex, and demultiplex optical signals. NEs 250 may process andtransmit optical signals to other NEs 250 throughout optical network 240in order to deliver optical transmissions.

FIG. 2B is a diagram of example devices of optical network 240 that maybe monitored and/or configured according to implementations describedherein. One or more devices illustrated in FIG. 2B may operate withinoptical network 240, and may correspond to NEs 250. Optical network 240may include one or more optical transmitter devices 260-1 through 260-M(M≧1) (hereinafter referred to individually as “Tx device 260” andcollectively as “Tx devices 260”), one or more super-channels 265-1through 265-M (M≧1) (hereinafter referred to individually as“super-channel 265” and collectively as “super-channels 265”), amultiplexer (“MUX”) 270, an OADM 275, a demultiplexer (“DEMUX”) 280, andone or more optical receiver devices 285-1 through 285-M (M≧1)(hereinafter referred to individually as “Rx device 285” andcollectively as “Rx devices 285”).

The number of devices illustrated in FIG. 2B is provided for explanatorypurposes. In practice, there may be additional devices, fewer devices,different devices, or differently arranged devices than are shown inFIG. 2B. Furthermore, two or more of the devices illustrated in FIG. 2Bmay be implemented within a single device, or a single deviceillustrated in FIG. 2B may be implemented as multiple, distributeddevices. Additionally, one or more of the devices illustrated in FIG. 2Bmay perform one or more functions described as being performed byanother one or more of the devices illustrated in FIG. 2B. Devicesillustrated in FIG. 2B may interconnect via wired connections (e.g.,fiber-optic connections).

Tx device 260 may correspond to NE 250. For example, Tx device 260 mayinclude an optical transmitter and/or an optical transceiver thatgenerates an optical signal. One or more optical signals may be carriedvia super-channel 265. In some implementations, Tx device 260 may beassociated with one super-channel 265. Additionally, or alternatively,Tx device 260 may be associated with multiple super-channels 265.Additionally, or alternatively, multiple Tx devices 260 may beassociated with one super-channel 265.

FIG. 2C is a diagram of example super-channels 265 that may be monitoredand/or configured according to implementations described herein. Asuper-channel, as used herein, may refer to multiple optical carriersthat are simultaneously transported over the same optical waveguide(e.g., a single mode optical fiber). Each optical carrier included in asuper-channel may be associated with a particular optical wavelength (orset of optical wavelengths). The multiple optical carriers may becombined to create a super-channel using wavelength divisionmultiplexing. For example, the multiple optical carriers may be combinedusing dense wavelength division multiplexing, in whichcarrier-to-carrier spacing may be less than 1 nanometer. In someimplementations, each optical carrier may be modulated to carry anoptical signal.

An example frequency and/or wavelength spectrum associated withsuper-channels 265 is illustrated in FIG. 2C. In some implementations,the frequency and/or wavelength spectrum may be associated with aparticular optical spectrum (e.g., C Band, C+Band, CDC Band, etc.). Asillustrated, super-channel 265-1 may include multiple optical carriers290, each of which corresponds to a wavelength λ (e.g., λ₁, λ₂, throughλ₁₀) within a first wavelength band. Similarly, super-channel 265-M mayinclude multiple optical carriers 290, each of which corresponds to awavelength λ (e.g., λ_(Y-X) through λ_(Y)) within a second wavelengthband. The quantity of illustrated optical carriers 290 per super-channel265 is provided for explanatory purposes. In practice, super-channel 265may include any quantity of optical carriers 290.

Optical carrier 290 may be associated with a particular frequency and/orwavelength of light. In some implementations, optical carrier 290 may beassociated with a frequency and/or wavelength at which the intensity oflight carried by optical carrier 290 is strongest (e.g., a peakintensity, illustrated by the peaks on each optical carrier 290). Insome implementations, optical carrier 290 may be associated with a setof frequencies and/or a set of wavelengths centered at a centralfrequency and/or wavelength. The intensity of light at the frequenciesand/or wavelengths around the central frequency and/or wavelength may beweaker than the intensity of light at the central frequency and/orwavelength, as illustrated.

In some implementations, the spacing between adjacent wavelengths (e.g.,λ₁ and λ₂) may be equal to or substantially equal to a bandwidth (or bitrate) associated with a data stream carried by optical carrier 290. Forexample, assume each optical carrier 290 included in super-channel 265-1(e.g., λ₁ through λ₁₀) is associated with a 50 Gigabit per second(“Gbps”) data stream. In this example, super-channel 265-1 may have acollective data rate of 500 Gbps (e.g., 50 Gbps×10). In someimplementations, the collective data rate of super-channel 265 may begreater than or equal to 100 Gbps. Additionally, or alternatively, thespacing between adjacent wavelengths may be non-uniform, and may varywithin a particular super-channel band (e.g., super-channel 265-1). Insome implementations, optical carriers 290 included in super-channel 265may be non-adjacent (e.g., may be associated with non-adjacentwavelengths in an optical spectrum).

Returning to FIG. 2B, each super-channel 265 may be provisioned inoptical network 240 as one optical channel and/or as an individualoptical channel. Provisioning of an optical channel may includedesignating an optical route and/or path for the optical channel throughoptical network 240. For example, an optical channel may be provisionedto be transmitted via a set of NEs 250. In some implementations, NEs 250may be configured as a ring. Additionally, or alternatively, NEs 250 maybe configured in a point-to-point configuration. Provisioning may bereferred to as “allocating” and/or “allocation” herein. Even though eachsuper-channel 265 is a composite of multiple optical carriers 290, theoptical carriers 290 included in super-channel 265 may be routedtogether through optical network 240. Additionally, or alternatively,super-channel 265 may be managed and/or controlled in optical network240 as though it included one optical channel and/or one optical carrierat one wavelength.

MUX 270 may correspond to NE 250. For example, MUX 270 may include anoptical multiplexer that combines multiple input super-channels 265 fortransmission over an output fiber.

OADM 275 may correspond to NE 250. For example, OADM 275 may include aremotely reconfigurable optical add-drop multiplexer. OADM 275 maymultiplex, de-multiplex, add, drop, and/or route multiple super-channels265 into and/or out of a fiber (e.g., a single mode fiber). Asillustrated, OADM 275 may drop super-channel 265-1 from a fiber, and mayallow super-channels 265-2 through 265-M to continue propagating towardRx device 285. Dropped super-channel 265-1 may be provided to a device(not shown) that may demodulate and/or otherwise process super-channel265-1 to output the data stream carried by super-channel 265-1. Asillustrated, super-channel 265-1 may be provisioned for transmissionfrom Tx device 260-1 to OADM 275, where super-channel 265-1 may bedropped.

As further illustrated in FIG. 2B, OADM 275 may add super-channel 265-1′(e.g., 265-1 ^(prime)) to the fiber. Super-channel 265-1′ may includeoptical carriers 290 at the same or substantially the same wavelengthsas super-channel 265-1. Super-channel 265-1′ and super-channels 265-2through 265-M may propagate to DEMUX 280.

DEMUX 280 may correspond to NE 250. For example, DEMUX 280 may includean optical de-multiplexer that separates multiple super-channels 265carried over an input fiber. For example, DEMUX 280 may separatesuper-channels 265-1′ and super-channels 265-2 through 265-M, and mayprovide each super-channel 265 to a corresponding Rx device 285.

Rx device 285 may correspond to NE 250. For example, Rx device 285 mayinclude an optical receiver and/or an optical transceiver that receivesan optical signal. One or more optical signals may be received at Rxdevice 285 via super-channel 265. Rx device 285 may convert asuper-channel 265 into one or more electrical signals, which may beprocessed to output the information associated with each data streamcarried by optical carriers 290 included in super-channel 265. In someimplementations, Rx device 285 may be associated with one super-channel265. Additionally, or alternatively, Rx device 285 may be associatedwith multiple super-channels 265. Additionally, or alternatively,multiple Rx devices 285 may be associated with one super-channel 265.

FIG. 3 is a diagram of example components of a device 300. Device 300may correspond to NPS 210, NA 220, user device 230, and/or NE 250.Additionally, or alternatively, each of NPS 210, NA 220, user device230, and/or NEs 250 may include one or more devices 300 and/or one ormore components of device 300.

Device 300 may include a bus 310, a processor 320, a memory 330, aninput component 340, an output component 350, and a communicationinterface 360. In some implementations, device 300 may includeadditional components, fewer components, different components, ordifferently arranged components than those illustrated in FIG. 3.

Bus 310 may include a path that permits communication among thecomponents of device 300. Processor 320 may include a processor, amicroprocessor, and/or any processing logic (e.g., a field-programmablegate array (“FPGA”), an application-specific integrated circuit(“ASIC”), etc.) that may interpret and execute instructions. Memory 330may include a random access memory (“RAM”), a read only memory (“ROM”),and/or any type of dynamic or static storage device (e.g., a flash,magnetic, or optical memory) that may store information and/orinstructions for use by processor 320.

Input component 340 may include any mechanism that permits a user toinput information to device 300 (e.g., a keyboard, a keypad, a mouse, abutton, a switch, etc.). Output component 350 may include any mechanismthat outputs information (e.g., a display, a speaker, one or morelight-emitting diodes (“LEDs”), etc.). Communication interface 360 mayinclude any transceiver-like mechanism, such as a transceiver and/or aseparate receiver and transmitter, that enables device 300 tocommunicate with other devices and/or systems, such as via a wiredconnection, a wireless connection, or a combination of wired andwireless connections. For example, communication interface 360 mayinclude mechanisms for communicating with another device and/or systemvia a network, such as optical network 240. Additionally, oralternatively, communication interface 360 may be a logical componentthat includes input and output ports, input and output systems, and/orother input and output components that facilitate the transmission ofdata to and/or from other devices, such as an Ethernet interface, anoptical interface, a coaxial interface, an infrared interface, a radiofrequency (“RF”) interface, a universal serial bus (“USB”) interface, orthe like.

Device 300 may perform various operations described herein. Device 300may perform these operations in response to processor 320 executingsoftware instructions contained in a computer-readable medium, such asmemory 330. A computer-readable medium may be defined as anon-transitory memory device. A memory device may include space within asingle storage device or space spread across multiple storage devices.

Software instructions may be read into memory 330 from anothercomputer-readable medium or from another device via communicationinterface 360. Software instructions stored in memory 330 may causeprocessor 320 to perform processes that are described herein.Additionally, or alternatively, hardwired circuitry may be used in placeof or in combination with software instructions to implement processesdescribed herein. Thus, implementations described herein are not limitedto any specific combination of hardware circuitry and software.

FIG. 4 is a diagram of example functional components of a device 400that may correspond to NA 220 and/or user device 230. As illustrated,device 400 may include a network configuration manager 410, a graphicaluser interface (“GUI”) manager 420, and a network configurer 430. Eachof functional components 410-430 may be implemented using one or morecomponents of device 300. NA 220 and/or user device 230 may individuallyinclude all of the functional components illustrated in FIG. 4, or thefunctional components illustrated in FIG. 4 may be distributedsingularly or duplicatively in any manner between the devicesillustrated in FIG. 2A and/or FIG. 2B. In some implementations, NA 220and/or user device 230 may include other functional components (notshown) that aid in managing optical network configurations andallocating optical network resources.

Network configuration manager 410 (“NCM 410”) may perform operationsassociated with managing a network configuration. In someimplementations, NCM 410 may receive network configuration informationfrom NPS 210 and/or NEs 250.

Network configuration information received from NPS 210 may include aquantity, location, capacity, and/or configuration of NEs 250;characteristics and/or configurations (e.g., capacity) of super-channelsbetween NEs 250; traffic demands of NEs 250 and/or super-channelsbetween NEs 250, and/or any other network configuration informationassociated with optical network 240 (e.g., optical deviceconfigurations, digital device configurations, etc.). In someimplementations, a user may model and/or plan a configuration of anoptical network 240 using NPS 210. NCM 410 may receive the networkconfiguration data modeled and/or planned using NPS 210, thus providinginitial network configuration information to NCM 410.

The initial network configuration information provided to NCM 410 may besupplemented with network configuration information received from NEs250. For example, NEs 250 may provide real-time network deploymentinformation to update the initial network configuration informationprovided by NPS 210. For example, NCM 410 may receive networkconfiguration information from NEs 250 that identifies newly-deployedNEs 250 and/or new super-channels between NEs 250. Additionally, oralternatively, NCM 410 may receive other network configurationinformation from NEs 250, such as super-channel allocation informationthat identifies super-channels that are available for opticaltransmission, assigned to transmit optical signals, currently being usedto transmit optical signals, and/or blocked from transmitting opticalsignals.

NCM 410 may transmit the network configuration information received fromNPS 210 and/or NEs 250 to GUI manager 420 so that a GUI providingnetwork configuration information may be updated (e.g., on NA 220 and/oruser device 230).

GUI manager 420 may perform operations associated with managing agraphical user interface that provides network configuration informationand aids in changing a network configuration. GUI manager 420 mayreceive network configuration information from NCM 410, and may providethe network configuration information for display on a device (e.g., NA220 and/or user device 230). Additionally, or alternatively, GUI manager420 may receive information associated with changes to a networkconfiguration, such as an allocation of super-channels between NEs 250,from a user interacting with a GUI (e.g., via NA 220 and/or user device230). GUI manager 420 may provide the information associated with thenetwork configuration changes to network configurer 430 so that opticalnetwork 240 and/or NEs 250 may be configured in accordance with thechanges.

Network configurer 430 may perform operations associated withconfiguring an optical network and/or network entities associated withan optical network. For example, network configurer 430 may aid inconfiguring optical network 240 and/or NEs 250. Network configurer 430may receive information associated with network configuration changesfrom GUI manager 420. Network configurer 430 may communicate theinformation associated with the changes to NEs 250 (and/or other devicesin optical network 240) so that NEs 250 may adjust their configurationin accordance with the network configuration changes. For example,network configurer 430 may provide instructions to NEs 250 that indicatethat NEs 250 are to reserve capacity (e.g., bandwidth) over one or moresuper-channels connecting NEs 250. In some implementations, networkconfigurer 430 may receive information validating a changedconfiguration from NEs 250, and may provide the configuration validationinformation to GUI manager 420 so that the validated changes may bedisplayed on a GUI (e.g., on NA 220 and/or user device 230).

FIG. 5 is a diagram of example super-channel types 500 that may be usedto allocate optical network capacity. A super-channel represents a highcapacity channel containing multiple optical carriers that are co-routedthrough an optical network as a single entity. Super-channel types mayhave different characteristics depending on how many optical carriersare multiplexed together to form a super-channel, a type of modulationformat used to aggregate the carriers, an amount of bandwidth allocatedto the super-channel, how the super-channel is allocated over thespectrum (e.g., contiguous spectrum allocation over contiguous spectralslices, split spectrum allocation over non-contiguous spectral slices,etc.), and/or other characteristics that may be used to differentiatesuper-channels.

Modulation formats used to multiplex optical carriers intosuper-channels may include binary phase-shift keying (“BPSK”),differential phase-shift keying (“DPSK”), quadrature phase-shift keying(“QPSK”), quadrature amplitude modulation (“QAM”), 3QAM, 8QAM, 16QAM,etc. The abbreviation “xPSK” may be used herein to refer to any type ofphase-shift keying modulation format.

A spectral slice (a “slice”) may represent a spectrum of a particularsize in a frequency band (e.g., 12.5 gigahertz (“GHz”), 6.25 GHz, etc.).For example, FIG. 5 shows a 4.8 terahertz (“THz”) frequency bandconsisting of 384 spectral slices. In this example, each spectral slicerepresents 12.5 GHz of the 4.8 THz spectrum. A super-channel may includea different quantity of spectral slices depending on the super-channeltype. For example, super-channel type 510 includes 16 spectral slicesper super-channel, for a total of 24 super-channels in the 4.8 THz/384spectral slice frequency band (16×24=384).

Super-channel type 510 may represent a super-channel with a bandwidth of1000 Gbps (e.g., 1 Terabit per second, “Tbps”) modulated using 16QAM(identified as “1000-16QAM”). Super-channel type 520 may represent asuper-channel with a bandwidth of 1000 Gbps (1 Tbps) modulated using8QAM (identified as “1000-8QAM”). Super-channel type 530 may represent asuper-channel with a bandwidth of 1000 Gbps (1 Tbps) modulated using PSK(e.g., QPSK, BPSK, DPSK, represented generally by “xPSK”) (identified as“1000-xPSK”). In some implementations, super-channel types 510-530 mayrepresent super-channels with bandwidths other than 1000 Gbps.Super-channels may be identified by the bandwidth and modulation typeassociated with the super-channel. For example, a super-channel with abandwidth of 1000 Gbps that uses 16QAM modulation may be identified as“1000-16QAM.”

As illustrated by box 580, super-channel types may include a differentquantity of spectral slices per super-channel. For example, twosuper-channels of type 510 may include the same number of spectralslices as one super-channel of type 530. Super-channel type 510 mayinclude 16 contiguous spectral slices per super-channel. Super-channeltype 520 may include 21 contiguous spectral slices per super-channelSuper-channel type 530 may include 32 contiguous spectral slices persuper-channel.

Super-channel type 540 may represent a super-channel with a bandwidth of500 Gbps allocated over contiguous spectral slices (e.g., contiguousspectrum, or “CS”), and modulated using, for example, either PSK(identified as “500-xPSK CS”) or 3QAM (identified as “500-3QAM CS”)(collectively identified as “500-xPSK/3QAM CS”). Super-channel type 540may include 20 contiguous spectral slices per super-channel. Contiguousspectrum may identify super-channels where every spectral slice includedin the super-channel is contiguous (e.g., super-channel 1 ofsuper-channel type 540 includes spectral slices 1-20). In someimplementations, super-channel type 540 may represent super-channelswith bandwidths other than 500 Gbps (e.g., 250 Gbps, 375 Gbps, etc.).

Super-channel type 550 may represent a super-channel with a bandwidth of500 Gbps allocated over non-contiguous spectral slices routed together(e.g., split spectrum, or “SS”), and modulated using, for example,either PSK (identified as “500-xPSK SS”) or 3QAM (identified as“500-3QAM SS”) (collectively identified as “500-xPSK/3QAM SS”).Super-channel type 550 may include 40 non-contiguous (e.g., splitspectrum) spectral slices per super-channel. Split spectrum may identifysuper-channels including spectral slices that are not contiguous, butare routed together (e.g., super-channel 1 of super-channel type 550,illustrated in the figure as “1a” and “1b,” includes spectral slices1-20 and 41-60).

Super-channel type 560 may represent Optical Carrier Groups (“OCG”). OCGsuper-channels may be allocated over non-contiguous sets of slices(e.g., ten non-contiguous sets of two adjacent spectral slices).Super-channel type 560 may represent 16 OCG super-channels.

Super-channel type 570 may represent transmissions over a route and/orlightpath defined by a custom channel plan. A custom channel plan mayallow transmission over any set of spectral slices (e.g., auser-specified set of spectral slices).

FIG. 6 is a diagram of an example user interface 600 (“UI 600”) forproviding network configuration information. In some implementations, UI600 may be displayed by NA 220 and/or user device 230. As illustrated,UI 600 may include a node display element 605, a component displayelement 610, super-channel display elements 615-635, allocation displayelements 640 and 645, a termination point display element 650, anadd/drop display element 655, an express route display element 660,local route identifier elements 665 and 670, alert elements 675-690, andselected super-channel type identifier element 695. Additionally, oralternatively, UI 600 may include fewer elements, additional elements,different elements, or differently arranged elements than thoseillustrated in FIG. 6.

UI 600 may provide information associated with NEs 250 and/orsuper-channels between NEs 250. In some implementations, UI 600 mayprovide information received from NCM 410, GUI manager 420, and/ornetwork configurer 430. UI 600 may be updated in real-time and/orperiodically to provide current network configuration information.Additionally, or alternatively, UI 600 may receive inputs (e.g.,super-channel allocations) from a user for transmission via GUI manager420 to network configurer 430 and/or NEs 250.

UI 600 may provide a mechanism (e.g., a button, an icon, a link, a textbox, etc.) for a user to specify NEs 250 to display on UI 600. UI 600may display all of the user-specified NEs 250 or a portion of theuser-specified NEs. The portion of the user-specified NEs 250 that aredisplayed may include a source NE 250 where a transmission is initiatedand/or a destination NE 250 where a transmission terminates. UI 600 maydisplay user-specified NEs 250 based on user selection of particular NEs250, user selection of a route associated with particular NEs 250, userselection of one or more super-channels associated with particular NEs250, user selection of one or more components associated with particularNEs 250, and/or user selection of other information associated withparticular NEs 250.

Node display element 605 may provide information associated with networknodes, such as NEs 250. For example, node display element 605 maydisplay a representation of NEs 250 associated with a particular opticalroute (e.g., a user-specified optical lightpath connecting multiple NEs250), an identification of the displayed NEs 250 (e.g., NEs 250-1,250-2, and 250-3, as illustrated), a representation of components of thedisplayed NEs 250, and/or other information associated with NEs 250.Node display element 605 may display particular NEs 250 in opticalnetwork 240 based on a user selection of NEs 250, a user selection of anoptical route associated with NEs 250, a user selection of a fiberassociated with NEs 250, and/or a user selection of other informationassociated with NEs 250.

Component display element 610 may provide information associated withcomponents of displayed NEs 250. For example, component display element610 may display a representation of one or more components connected toa transmission fiber that connects the displayed NEs 250 (e.g., aninline amplifier module (“IAM”), an inline Raman module, a flex ROADMmodule (“FRM”), a field replaceable unit, etc.). Additionally, oralternatively, component display element 610 may display anidentification of the component (e.g., IAMs “2-A-1” and “2-A-2,” FRMs“1-A-5” and “1-A-6,” as illustrated).

Super-channel display elements (“SDE” or “SDEs”) 615-635 may provide arepresentation of one or more super-channels that may transmit databetween displayed NEs 250. SDE 615 may display a quantity ofsuper-channels between displayed NEs 250 based on a user selection of asuper-channel type and a quantity of spectral slices included in theselected super-channel type. For example, super-channel type “500-xPSK”includes 20 spectral slices per super-channel, which allows for 19super-channels in a frequency band occupying 384 slices. If a userselects super-channel type “500-xPSK,” SDE 615 may display 19super-channels (labeled “SCH” in the figures), as illustrated.

SDE 615 may display a super-channel in a particular manner depending oncharacteristics of the super-channel, such as a quantity of spectralslices associated with the super-channel (e.g., 20 slices, 32 slices,etc.), a relative position of the associated spectral slices within anoptical spectrum (e.g., slices 1-20 may occupy a different wavelengthand/or position than slices 21-54), a super-channel type associated withthe super-channel (e.g., “500-xPSK”), an allocation status associatedwith the super-channel (e.g., assigned, used, blocked, and/oravailable), an alert status associated with the super-channel (e.g., inservice, out of service, misconfigured, not optically viable, and/orother alerts), and/or other information associated with a displayedsuper-channel.

SDE 615 may display a super-channel in a particular and/or relativeposition (e.g., a position on a display) to convey informationassociated with the super-channel. For example, SDE 615 may displaysuper-channels in a particular position based on the spectral slicesassociated with the super-channel. In some implementations,super-channels may be displayed in an order or a sequence, with thefirst super-channel (e.g., SCH 1) including spectral slices at thebeginning of an optical spectrum (e.g., slice 1), and the lastsuper-channel (e.g., SCH 19) including spectral slices at the end of thespectrum (e.g., slice 384, or in the illustrated scenario, slice 380).As illustrated, SDE 615 may display a first super-channel (SCH 1) on topof a stack of super-channels when the first super-channel is associatedwith spectral slices 1-32.

SDE 615 may display a super-channel using a particular and/or relativesize to convey information associated with the super-channel. Forexample, SDE 615 may display a super-channel using a size that isproportional to the quantity of spectral slices included in thesuper-channel. The quantity of spectral slices included in asuper-channel may depend on a super-channel type. As illustrated, SDE620 may display a super-channel (SCH 1) of type “1000-xPSK,” whichincludes 32 spectral slices, and SDE 625 may display a super-channel(SCH 4) of type “500-3QAM CS,” which includes 20 spectral slices. SCH 1may be displayed in a more prominent manner (e.g., larger, bolder, in adifferent color, etc.) than SCH 4 because SCH 1 includes more spectralslices (e.g., has a greater capacity) than SCH 4, as illustrated.

In the figures, every super-channel may not be illustrated as preciselyproportional to the quantity of slices that make up the super-channel.However, SDE 615 may display super-channels of the same type using thesame size, and may display a super-channel size as proportional to thequantity of slices included in the super-channel.

SDE 615 may display a super-channel using a particular label to conveyinformation associated with the super-channel. A super-channel label mayprovide an indication of a super-channel identifier (e.g., a number)associated with a super-channel, a super-channel type associated with asuper-channel, a capacity of a super-channel, an allocation statusassociated with a super-channel, an alert status associated with asuper-channel, and/or other characteristics associated with asuper-channel. For example, SDE 620 may display a super-channel labelthat provides an indication of a super-channel identifier associatedwith a super-channel (e.g., “SCH 1”), a bandwidth associated with thesuper-channel (e.g., “1000” Gbps), a modulation type associated with thesuper-channel (e.g., “xPSK”), and/or a super-channel type associatedwith the super-channel (e.g., “1000-xPSK”), as illustrated.

SDE 615 may display a super-channel using a particular color and/orpattern in order to convey information associated with thesuper-channel. For example, SDE 615 may display a super-channel using aparticular color to indicate an allocation status associated with thesuper-channel. As illustrated, SDE 620 may display an assignedsuper-channel using a first color, SDE 625 may display a usedsuper-channel using a second color, SDE 630 may display blocked spectralslices using a third color, and SDE 635 may display an availablesuper-channel using a fourth color.

An allocation status may include, for example, assigned, used, blocked,and/or available. In some implementations, an assigned status mayindicate that a super-channel has been assigned to transmit opticalsignals, but is not currently transmitting optical signals.Additionally, or alternatively, an assigned status may indicate that asuper-channel is associated with a line module (e.g. an FRM) and/or across-connect (e.g., a termination point on an FRM) on one end (e.g., onNE 250-1), but is not associated with a line module and/or across-connect on the other end (e.g., on NE 250-2). SDE 620 may displayassigned super-channels using a first color (e.g., green or light gray).

In some implementations, a used status may indicate that a super-channelis currently transmitting data. Additionally, or alternatively, a usedstatus may indicate that a super-channel is associated with linesmodules (e.g., FRMs) and/or cross-connects (e.g., termination points onFRMs) on both NEs 250 that the super-channel connects (e.g., NE 250-1and NE 250-2). SDE 625 may display used super-channels using a secondcolor (e.g., dark gray).

In some implementations, a blocked status may indicate that asuper-channel and/or one or more spectral slices are unavailable forallocation. For example, a super-channel may be blocked when there isnot enough capacity to support allocation of the super-channel and/orspectral slices using a selected super-channel type. As illustrated, SDE615 may aid in allocating super-channels of type “500-xPSK,” whichinclude 20 spectral slices per super-channel. For these super-channeltypes (“500-xPSK”), 19 super-channels may be allocated along particularslices of an optical spectrum (e.g., slices 1-20 for SCH 1, slices 21-40for SCH 2, slices 41-60 for SCH 3, etc.). As illustrated, SDE 620 maydisplay an assigned super-channel of type “1000-xPSK,” which includes 32slices allocated to slices 1-32. This assignment uses SCH 1 (slices1-20) and a portion of SCH 2 (slices 21-32 of SCH 2, which includesslices 21-40), leaving slices 33-40 available for allocation. However,super-channels of type “500-xPSK” require 20 slices that may only beallocated on particular sets of slices (e.g., on slices 1-20, 21-40,41-60, 61-80, etc.). Thus, “500-xPSK” cannot be allocated on slices33-40, and SDE 630 may display slices 33-40 as blocked (e.g., using athird color, such as black), as illustrated. Additionally, oralternatively, a blocked status may indicate that a super-channel and/orspectral slices have not been configured for allocation between NEs 250.

In some implementations, an available status may indicate that asuper-channel is available for data transmission (e.g., thesuper-channel is not assigned, used, or blocked). Additionally, oralternatively, an available status may indicate that a super-channel isnot associated with a line module or cross-connect on either NE 250 thatthe super-channel connects. As illustrated, SDE 635 may displayavailable super-channels using a fourth color (e.g., white).

Allocation display elements (“ADE” or “ADEs”) 640 and 645 may provide asummary of allocation statuses for displayed spectral slices and/ordisplayed super-channels. ADE 640 may indicate a quantity of displayedspectral slices having a particular allocation status. As illustrated,ADE 640 may display an indication that there are 384 spectral slices ona fiber connecting NE 250-1 to NE 250-2, with 40 used slices, 52assigned slices, 8 blocked slices, and 284 available slices. ADE 645 mayindicate a quantity of displayed super-channels having a particularallocation status. As illustrated, ADE 645 may display an indicationthat there are 19 super-channels connecting FRM 1-A-5 on NE 250-1 to FRM1-A-5 on NE 250-2, with 5 allocated (e.g., used, assigned, and/orblocked) super-channels and 14 available super-channels. In someimplementations, ADEs 640 and 645 may provide a summary of allocationstatuses across a span of multiple NEs 250.

Termination point display element (“TPDE”) 650 may provide an indicationof super-channel connection termination points (e.g., ports) on an FRMassociated with a displayed NE 250. TPDE 650 may provide an indicationof allocated termination points. For example, TPDE 650 may display aline connecting allocated termination points to allocatedsuper-channels. In some implementations, the line may be displayed inthe same color as the super-channel to which it is connected in order toindicate an allocation status of the termination point. Additionally, oralternatively, termination points that have not been allocated may bedisplayed without a line connecting the termination point to asuper-channel.

Add/drop display element (“ADDE”) 655 may provide an indication oftransmissions (e.g., via super-channels) that are added and/or droppedby a displayed NE 250. In some implementations, ADDE 655 may display aparticular shape to indicate an add/drop location of a transmission. Asillustrated, ADDE 655 may display a circle on NE 250-3 to indicate thatthe transmission associated with “SCH 1: 1000-xPSK” between NE 250-2 andNE 250-3 is added or dropped at NE 250-3. In some implementations, ADDE655 may use a different indicator for an added transmission than for adropped transmission.

Express route display element (“ERDE”) 660 may provide an indication ofa route (e.g., a super-channel) allocated between a component that isdisplayed on UI 600 (e.g., FRM 1-A-6 on NE 250-2) and a component thatis not displayed on UI 600. For example, UI 600 displays FRMs 1-A-5 and1-A-6 on NE 250-2. There may be other FRMs on NE 250-2 not displayed byUI 600. ERDE 660 may provide an indication that a route has beenallocated between FRM 1-A-6 on NE 250-2 (displayed by UI 600) and one ofthe other FRMs on NE 250-2 that is not displayed by UI 600. In someimplementations, ERDE 660 may display a particular shape to provide thisindication. As illustrated, ERDE 660 may display a square on NE 250-2 toindicate that the transmission associated with “SCH 1: 1000-xPSK”between NE 250-2 and NE 250-3 is routed between FRM 1-A-6 on NE 250-2and another FRM (one that is not displayed on UI 600) on NE 250-2 otherthan FRM 1-A-5 (which is displayed on UI 600).

Local route identifier element (“LRIE”) 665 may provide an indication ofa route allocated between displayed components (e.g., displayed FRMs onNE 250). For example, LRIE 665 may display a line connecting allocatedsuper-channels. In some implementations, the line may be displayed inthe same color as a super-channel and/or super-channels to which it isconnected in order to indicate an allocation status of the route. Asillustrated, LRIE 665 may display a line on NE 250-2 connecting SCH 14between NE 250-1 and NE 250-3. The line connects termination points onFRM 1-A-5 and FRM 1-A-6 on NE 250-2 to indicate that the route isallocated between these FRMs (1-A-5 and 1-A-6 on NE 250-2, both of whichare displayed).

LRIE 670 may provide an indication of a route available for allocationbetween displayed components (e.g., displayed FRMs on NE 250). Forexample, LRIE 670 may display a line connecting available super-channelsand/or termination points. In some implementations, the line may be adashed line. As illustrated, LRIE 670 may display a dashed line on NE250-2 connecting SCH 19 between NE 250-1 and NE 250-3. The line connectstermination points on FRM 1-A-5 and FRM 1-A-6 on NE 250-2 to indicatethat a route is available between these FRMs (1-A-5 and 1-A-6 on NE250-2, both of which are displayed). Additionally, or alternatively,available routes may be displayed without a line connecting availablesuper-channels and/or termination points. In some implementations, LRIE670 may display a line connecting SDE 615 and TPDE 650 to indicatecontinuity across one or more spans of optical links (e.g., to indicatethat SCH 19 between NE 250-1 and NE 250-2 continues in the route as SCH19 between NE 250-2 and NE 250-3).

Alert elements 675-690 may provide an indication of alerts (e.g.,errors, notifications, alarms, warnings, etc.) associated with adisplayed super-channel, a displayed component, and/or a displayed NE250. Alerts may be associated with a cross-connect problem associatedwith an NE 250, a service state associated with a super-channel, aconfiguration problem associated with a super-channel, an opticalviability problem associated with a super-channel, and/or any otheralert that may convey information (e.g., an issue, problem, alarm,error, etc.) associated with an optical network.

Alert element 675 may provide an indication that a super-channel is notconnected to a cross-connect (e.g., is not being added, dropped, orrouted by NE 250). Additionally, or alternatively, alert element 675 mayindicate that a line module has not been installed. As illustrated,alert element 675 may display a question mark or another notification ata cross-connect location on NE 250-3 to indicate that a transmissionassociated with SCH 14 is not being routed, added, or dropped by NE250-3.

Alert element 680 may provide an indication of a service state of asuper-channel. A service state may include in-service or out-of-service.As illustrated, alert element 680 may display an “X” or anothernotification on SCH 14 between NE 250-2 and NE 250-3 to indicate thatSCH 14 is out of service between NE 250-2 and NE 250-3. Additionally, oralternatively, alert element 680 may indicate that a super-channel isout of service along a route associated with the super-channel (e.g.,SCH 14 between NE 250-1 and NE 250-3, as illustrated).

Alert element 685 may provide an indication of a configuration problemof a super-channel. A configuration problem may indicate that amodulation type configured on a cross-connect at one end of a route doesnot match a modulation type configured on a cross-connect at the otherend of the route. As illustrated, alert element 685 may display anexclamation point or another notification on SCH 14 between NE 250-2 andNE 250-3 to indicate that the cross-connect on NE 250-2 is configuredfor one super-channel type (e.g., “500-xPSK”), and the cross-connect onNE 250-3 is configured for a different super-channel type (e.g.,“1000-xPSK”). In some implementations, SDE 615 may display asuper-channel between misconfigured cross-connects (e.g., SCH 14) usinga size based on the super-channel type that includes a larger quantityof spectra slices (e.g., displayed using a size based on super-channeltype “1000-xPSK” rather than “500-xPSK”). Additionally, oralternatively, alert element 685 may indicate that a super-channel isassociated with a configuration problem somewhere along a routeassociated with the super-channel (e.g., SCH 14 between NE 250-1 and NE250-3, as illustrated).

Alert element 690 may provide an indication of an optical viabilityproblem of a super-channel. An optical viability problem may indicatethat a super-channel cannot transmit light across a route without lossof data integrity due to errors, light degradation, etc. As illustrated,alert element 690 may display a double dagger (“s”) or anothernotification on SCH 14 between NE 250-2 and NE 250-3 to indicate thatSCH 14 is not optically viable for a particular data transmissionbetween NE 250-2 and NE 250-3. Additionally, or alternatively, alertelement 690 may indicate that a super-channel is associated with anoptical viability problem along a route associated with thesuper-channel (e.g., SCH 14 between NE 250-1 and NE 250-3, asillustrated).

Selected super-channel type identifier element 695 may identify auser-specified super-channel type. A user may specify a super-channeltype in order to allocate capacity to super-channels of the specifiedsuper-channel type. Super-channels representations displayed by SDE 615may change based on the specified super-channel type. As illustrated,selected super-channel type identifier element 695 may indicate that auser has selected a super-channel type “500-xPSK,” and SDE 615 maychange to allow a user to select available super-channels of type“500-xPSK” for allocation. SDE 615 may change the displayed quantity,position, size, and/or labels associated with the displayedsuper-channels based on characteristics associated with theuser-specified super-channel type.

FIG. 7 is a diagram of an example user interface 700 (“UI 700”) that mayaid a user in selecting a super-channel for allocating network capacity.In some implementations, UI 700 may be displayed by NA 220 and/or userdevice 230. As illustrated, UI 700 may include a selection element 710,a display element 720, and super-channel type selector elements (“STSE”or “STSEs”) 730-790. Additionally, or alternatively, UI 700 may includefewer elements, additional elements, different elements, or differentlyarranged elements than those illustrated in FIG. 7, such as elements605-695 of UI 600.

Selection element 710 may provide a mechanism (e.g., a button, an icon,a link, a drop-down menu, a text box, etc.) for a user to select asuper-channel type for capacity allocation. In some implementations,selection element 710 may display information associated withsuper-channel types that may be selected by a user in order to assist inallocating network capacity. The super-channel types displayed byselection element 710 may be based on super-channel types configured forallocation between displayed NEs 250 and/or configured for allocationover a user-selected route.

As illustrated, STSE 730 may correspond to super-channel type“500-xPSK/3QAM CS,” STSE 740 may correspond to super-channel type“500-xPSK/3QAM SS,” STSE 750 may correspond to super-channel type“1000-xPSK,” STSE 760 may correspond to super-channel type “1000-8QAM,”STSE 770 may correspond to super-channel type “1000-16QAM,” STSE 780 maycorrespond to a custom channel plan, and STSE 790 may correspond tosuper-channel type “OCG.”

Display element 720 may include elements 605-695, described herein inconnection with FIG. 6. Display element 720 may display particularelements and/or may display elements in a particular manner based on auser selection of a super-channel type (e.g., via selection element710). For example, a quantity, location, label, and/or size of one ormore super-channels displayed by display element 720 may change based ona super-channel type selected by a user. In some implementations, a usermay select a super-channel type using a mouse click (e.g., a mouse clickon one of STSEs 730-790 within selection element 710). Additionally, oralternatively, a user may select a super-channel type using a drop downbox, a combo box, a list box, a text box, etc.

FIG. 8 is a diagram of an example user interface 800 (“UI 800”) that mayaid a user in selecting a super-channel for allocating optical networkcapacity. In some implementations, UI 800 may be displayed by NA 220and/or user device 230. As illustrated, UI 800 may include selectionelement 710 and display element 720, as described herein in connectionwith FIG. 7. Additionally, or alternatively, UI 800 may includeavailability indicator 810, optical viability indicator 820, andselected super-channel indicator 830. Additionally, or alternatively, UI800 may include fewer elements, additional elements, different elements,or differently arranged elements than those illustrated in FIG. 8, suchas elements 605-695 of UI 600 and elements 730-790 of FIG. 7.

Elements displayed by UI 800, selection element 710, display element720, availability indicator 810, optical viability indicator 820, andselected super-channel indicator 830 may be based on a user selection ofSTSE 730, which corresponds to super-channel type “500-xPSK/3QAM CS.”For example, a user may click on STSE 730 within selection element 710,as illustrated by a mouse cursor within selection element 710. Displayelement 720 may provide information associated with availablesuper-channels, assigned super-channels, used super-channels, and/orblocked super-channels and/or spectral slices based on the userselection. For example, display element 720 may display availablesuper-channels (e.g., displayed in white) and blocked slices (e.g.,displayed in black) based on user selection of STSE 730 (which isassociated with 19 super-channels), as illustrated. In someimplementations, used super-channels and assigned super-channels may notchange based on the user selection.

Availability indicator 810 may identify super-channels of the selectedtype that are available for allocation across a desired optical route(here, from NE 250-1 to NE 250-2 to NE 250-3). An optical route mayinclude one or more super-channels that connect two or more NEs 250. Asillustrated, availability indicator 810 may indicate that super-channels5-7, 10-13, and 15-19 are available across the entirety of the desiredroute. Availability indictor 810 may use highlighting, outlining,labels, colors, and/or patterns to indicate super-channels that areavailable for allocation across the desired route. For example,availability indicator 810 may outline super-channels in selectionelement 710 that are available across the desired route, as illustrated.Additionally, or alternatively, availability indicator 810 may indicatesuper-channels that are available for allocation across a desired routein display element 720.

Optical viability indicator 820 may identify super-channels that areoptically viable across the entirety of the desired route. Opticalviability may refer to the ability of a super-channel to deliver lightacross the desired route without loss of data integrity due to errors,light degradation, etc. Optical viability indicator 820 may usehighlighting, outlining, labels, colors, and/or patterns to indicatesuper-channels that are optically viable for transporting data acrossthe desired route. For example, optical viability indicator 820 mayindicate that super-channels 6 and 10 are optically viable by labelingsuper-channels 6 and 10 with an asterisk (*) in selection element 710,as illustrated. In some implementations, a check mark and/or otherindicator may be used. Additionally, or alternatively, optical viabilityindicator 820 may indicate optically viable super-channels in displayelement 720.

Selected super-channel indicator 830 may identify user selection of aparticular super-channel for allocating a data transmission. In someimplementations, a user may select a particular super-channel byclicking on the super-channel within display element 720, as illustratedby a mouse cursor within display element 720. Additionally, oralternatively, a user may select a particular super-channel by clickingon the super-channel in selection element 710 (e.g., a second clickafter an initial click to select the super-channel type). Additionally,or alternatively, a user may select a particular super-channel forallocating a data transmission using a drop down box, a combo box, alist box, a text box, etc.

Selected super-channel indicator 830 may use highlighting, outlining,labels, colors, and/or patterns to indicate the super-channel that hasbeen selected by a user. For example, selected super-channel indicator830 may identify a user-selected super-channel (e.g., super-channel 6)by highlighting the super-channel in display element 720, asillustrated. Additionally, or alternatively, selected super-channelindicator 830 may indicate a user-selected super-channel in selectionelement 710.

FIG. 9 is a diagram of another example user interface 900 (“UI 900”)that may aid a user in selecting a super-channel for allocating opticalnetwork capacity. In some implementations, UI 900 may be displayed by NA220 and/or user device 230. As illustrated, UI 900 may includeallocation display elements 640 and 645, as described herein inconnection with FIG. 6. Additionally, or alternatively, UI 900 mayinclude selection element 710, display element 720, availabilityindicator 810, optical viability indicator 820, and selectedsuper-channel indicator 830, as described herein in connection withFIGS. 7 and 8. Additionally, or alternatively, UI 900 may include fewerelements, additional elements, different elements, or differentlyarranged elements than those illustrated in FIG. 9, such as elements605-695 of UI 600 and elements 730-790 of FIG. 7.

Elements displayed by UI 900, ADEs 640 and 645, selection element 710,display element 720, availability indicator 810, optical viabilityindicator 820, and selected super-channel indicator 830 may be based ona user selection of STSE 750, which corresponds to super-channel type“1000-xPSK.” For example, a user may click on STSE 750 within selectionelement 710, as illustrated by a mouse cursor within selection element710. Display element 720 may display available super-channels (e.g.,displayed in white) and blocked slices (e.g., displayed in black) basedon user selection of STSE 750 (which is associated with 12super-channels), as illustrated.

ADEs 640 and 645 may provide a summary of allocation statuses fordisplayed spectral slices and/or displayed super-channels. Asillustrated, ADE 640 may display an indication that there are 384spectral slices on a fiber connecting NE 250-1 to NE 250-2, with 52 usedslices, 52 assigned slices, 24 blocked slices, and 256 available slices.As illustrated, ADE 645 may display an indication that there are 12super-channels connecting FRM 1-A-5 on NE 250-1 to FRM 1-A-5 on NE250-2, with 4 allocated (e.g., used, assigned, and/or blocked)super-channels and 8 available super-channels.

Availability indicator 810 may identify super-channels of the selectedtype that are available for allocation across a desired route (here,from NE 250-1 to NE 250-2 to NE 250-3). As illustrated, availabilityindicator 810 may highlight super-channels 4, 6-8, and 10-12 inselection element 710 to indicate that those super-channels areavailable across the entirety of the desired route. Optical viabilityindicator 820 may indicate that super-channels 1, 4, and 7 are opticallyviable by labeling super-channels 1, 4, and 7 with an asterisk (*) inselection element 710, as illustrated.

Selected super-channel indicator 830 may identify a user-selectedsuper-channel (e.g., super-channel 7) by highlighting the selectedsuper-channel in display element 720, as illustrated. In someimplementations, a user may select a particular super-channel byclicking on the super-channel within display element 720, as illustratedby a mouse cursor within display element 720. Additionally, oralternatively, a user may select a particular super-channel by clickingon the super-channel in selection element 710 (e.g., a second clickafter an initial click to select the super-channel type). Additionally,or alternatively, a user may select a particular super-channel forallocating a data transmission using a drop down box, a combo box, alist box, a text box, etc.

FIG. 10 is a diagram of an example user interface 1000 (“UI 1000”) thatmay aid a user in selecting spectral slices for allocating opticalnetwork capacity. In some implementations, UI 1000 may be displayed byNA 220 and/or user device 230. As illustrated, UI 1000 may includeallocation display element 640, as described herein in connection withFIG. 6. Additionally, or alternatively, UI 1000 may include selectionelement 710, display element 720, availability indicator 810, opticalviability indicator 820, and selected super-channel indicator 830, asdescribed herein in connection with FIGS. 7 and 8. Additionally, oralternatively, UI 1000 may include fewer elements, additional elements,different elements, or differently arranged elements than thoseillustrated in FIG. 10, such as elements 605-695 of UI 600 and elements730-790 of FIG. 7.

Elements displayed by UI 1000, ADE 640, selection element 710, displayelement 720, availability indicator 810, optical viability indicator820, and selected super-channel indicator 830 may be based on a userselection of STSE 780, which corresponds to a custom channel plan. Forexample, a user may click on STSE 780 within selection element 710, asillustrated by a mouse cursor within selection element 710. A customchannel plan may allow a user to select specific spectral slices forallocation, rather than selecting a super-channel.

Display element 720 may display available spectral slices (e.g.,displayed in white) based on user selection of STSE 780, and may displayan indication of the slice numbers associated with the available slices(e.g., slices 33-40, 81-100, 201-256, and 321-384 between NE 250-1 andNE 250-2). In some implementations, a user may be required to select aminimum quantity of contiguous slices for allocation (e.g., fourcontiguous slices), and display element 720 may provide an indication ofblocked spectral slices (e.g., where there are less than four contiguousslices).

ADEs 640 may provide a summary of allocation statuses for displayedspectral slices. As illustrated, ADE 640 may display an indication thatthere are 384 spectral slices on a fiber connecting NE 250-1 to NE250-2, with 184 used slices, 52 assigned slices, 0 blocked slices, and148 available slices.

Availability indicator 810 may identify spectral slices that areavailable for allocation across a desired route (here, from NE 250-1 toNE 250-2 to NE 250-3). As illustrated, availability indicator 810 mayhighlight slices 33-40, 81-100, 201-256, and 321-384 on selectionelement 710 to indicate that those slices are available across theentirety of the desired route. Optical viability indicator 820 mayindicate that slices 201-256 are optically viable by labeling slices201-256 with an asterisk (*) in selection element 710, as illustrated.

Selected super-channel indicator 830 may indicate user-selected slices(e.g., slices 201-220) by highlighting the selected slices in displayelement 720, as illustrated. In some implementations, a user may selectparticular slices by clicking and dragging on available slices withindisplay element 720, as illustrated by a mouse cursor within displayelement 720. Additionally, or alternatively, a user may select aparticular super-channel by clicking and dragging on available slices inselection element 710 (e.g., a click and drag after an initial click toselect the super-channel type). In some implementations, a user mayclick on available slices, and UI 1000 may provide a pop-up boxdisplaying an indication of the first slice and the last slice of theselected available slices. UI 1000 may allow a user to adjust the firstand last slices (e.g., using a text box, a slider, a counter, etc.) inorder to select a set of slices for bandwidth allocation. Additionally,or alternatively, a user may select a particular super-channel forallocating a data transmission using a drop down box, a combo box, alist box, a text box, etc.

FIG. 11 is a diagram of an example user interface 1100 (“UI 1100”) thatmay aid a user in selecting a super-channel for allocating opticalnetwork capacity. In some implementations, UI 1100 may be displayed byNA 220 and/or user device 230. As illustrated, UI 1100 may includeselection element 710, display element 720, availability indicator 810,optical viability indicator 820, and selected super-channel indicator830, as described herein in connection with FIGS. 7 and 8. Additionally,or alternatively, UI 1100 may include fewer elements, additionalelements, different elements, or differently arranged elements thanthose illustrated in FIG. 11, such as elements 605-695 of UI 600 andelements 730-790 of FIG. 7.

Elements displayed by UI 1100, selection element 710, display element720, availability indicator 810, optical viability indicator 820, andselected super-channel indicator 830 may be based on a user selection ofSTSE 790, which corresponds to super-channel type “OCG.” For example, auser may click on STSE 790 within selection element 710, as illustratedby a mouse cursor within selection element 710. OCG super-channel typemay allow a user to allocate ten non-contiguous sets of slices, asillustrated in display element 720 (e.g., ten non-contiguous slicesbetween SCH 9 and SCH 19).

Display element 720 may display an indication of used OCGsuper-channels, assigned OCG super-channels (e.g., OCG super-channel 5,as illustrated), available OCG super-channels, and/or blocked OCGsuper-channels based on user selection of STSE 790. In someimplementations, spectral slices may be available for allocation tosuper-channel type “OCG,” and unavailable (e.g., blocked) for allocationto other super-channel types (e.g., “1000-xPSK,” “500 3QAM CS,” etc.).Display element 720 may display OCG super-channel allocation statuses(e.g., available or blocked) based on user selection of a super-channeltype.

Availability indicator 810 may identify OCG super-channels that areavailable for allocation across a desired route (here, from NE 250-1 toNE 250-2 to NE 250-3). As illustrated, availability indicator 810 mayhighlight OCG super-channels 6-8 and 13-16 on selection element 710 toindicate that those OCG super-channels are available across the entiretyof the desired route. Optical viability indicator 820 may indicate thatOCG super-channels 5 and 13 are optically viable by labeling OCGsuper-channels 5 and 13 with an asterisk (*) in selection element 710,as illustrated.

Selected super-channel indicator 830 may indicate user-selected slices(in this example, OCG super-channel 13) by highlighting the selectedslices in display element 720 and/or providing a separate indication ofthe selected OCG super-channel, as illustrated. In some implementations,a user may select a particular OCG super-channel by clicking on the OCGsuper-channel within selection element 710 (e.g., a second click afteran initial click to select the super-channel type). Additionally, oralternatively, a user may select a particular OCG super-channel forallocating a data transmission using a drop down box, a combo box, alist box, a text box, etc.

FIG. 12 is a diagram of an example user interface 1200 (“UI 1200”) thatmay aid a user in allocating optical network capacity. In someimplementations, UI 1200 may be displayed by NA 220 and/or user device230. As illustrated, UI 1200 may include a source identifier element1210, a destination identifier element 1220, a route information element1230, a route identifier element 1240, an administrator element 1250,and a circuit creation element 1260. Additionally, or alternatively, UI1200 may include fewer elements, additional elements, differentelements, or differently arranged elements than those illustrated inFIG. 12.

Source identifier element 1210 may provide a mechanism (e.g., a button,an icon, a text box, a link, etc.) for a user to select a source for anoptical data transmission. For example, source identifier element 1210may identify an NE 250 and/or a component of NE 250 (e.g., an FRM) as asource for a data transmission that is to be transmitted over asuper-channel. In some implementations, source identifier element 1210may be populated based on user selection of one or more elements of UIs600-1100. For example, a user may select NE 250-1 on node displayelement 605 and/or may select FRM 1-A-5 on component display element 610to populate source identifier element 1210 with a node identifier and/oran endpoint identifier, as illustrated.

Destination identifier element 1220 may provide a mechanism (e.g., abutton, an icon, a text box, a link, etc.) for a user to select adestination for an optical data. For example, destination identifierelement 1220 may identify an NE 250 and/or a component of NE 250 (e.g.,an FRM) as a destination for a data transmission that is to betransmitted over a super-channel. In some implementations, destinationidentifier element 1220 may be populated based on user selection of oneor more elements of UIs 600-1100. For example, a user may select NE250-3 on node display element 605 and/or may select FRM 1-A-5 oncomponent display element 610 to populate destination identifier element1220 with a node identifier and/or an endpoint identifier, asillustrated.

Route information element 1230 may provide a mechanism (e.g., a button,an icon, a text box, a link, etc.) for a user to select routeinformation for an optical transmission to be allocated. For example, auser may select a rate of a super-channel to be allocated, a modulationformat of a super-channel to be allocated, a super-channel type of asuper-channel to be allocated, a super-channel identifier of asuper-channel to be allocated, a spectral slice identifier of one ormore spectral slices to be allocated, an optically engineered lightpath(e.g., an “OEL,” which may be a particular route over NEs 250 andcomponents of NEs 250 using particular super-channels) associated with adata transmission to be allocated, etc. In some implementations, routeinformation element 1230 may be populated based on user selection of oneor more elements of UIs 600-1100. For example, a user may select asuper-channel rate, modulation format, and/or type (e.g., “500-xPSK”), asuper-channel identifier (e.g., “SCH 6”), one or more spectral slices(e.g., “slices 101-120”), and/or an OEL (e.g., “OEL-101”) on an elementof UIs 600-1100 (e.g., elements 615-635) to populate route informationelement 1230.

In some implementations, elements 1210-1230 may be populated by userselection of an available super-channel displayed by SDE 615. Selectionof an available super-channel may provide elements 1210-1230 withinformation associated with a source and/or destination node and/orendpoint associated with the selected super-channel; a bandwidth,modulation format, and/or super-channel type associated with theselected super-channel; a super-channel identifier associated with theselected super-channel; and/or any other information associated with theselected super-channel (e.g., information that may be used to allocatethe selected super-channel).

Additionally, or alternatively, elements 1210-1230 may be populated byuser selection of an available cross-connect (e.g., termination point)displayed by TPDE 650. Selection of an available cross-connect mayprovide elements 1210-1230 with information associated with a nodeand/or endpoint (e.g., a source node and/or endpoint) associated withthe selected cross-connect; a bandwidth, modulation format, and/orsuper-channel type associated with the selected cross-connect; asuper-channel associated with the selected cross-connect; asuper-channel identifier associated with the selected cross-connect; asecond cross-connect associated with the selected cross-connect; a nodeand/or endpoint associated with the second cross-connect (e.g., adestination node and/or endpoint); and/or any other informationassociated with the selected cross-connect (e.g., information that maybe used to allocate the selected cross-connect and/or a super-channelassociated with the selected cross-connect).

Route identifier element 1240 may provide a mechanism (e.g., a button,an icon, a text box, a link, etc.) for a user to input information thatidentifies the route and/or optical lightpath specified by elements1210-1230. For example, a user may input a circuit identifier and/or alabel for the route to be allocated.

Administrator element 1250 may provide a mechanism (e.g., a button, anicon, a text box, a link, etc.) for a user to change an administrativestate of a particular route and/or NEs 250 associated with a particularroute. An administrative state may include locked or unlocked. A lockedadministrative state may take NE 250 out of service, and may allow auser to change a configuration and/or a parameter associated with NE250. An unlocked administrative state may prevent a user from changingone or more parameters and/or configurations associated with NE 250. Insome implementations, NE 250 may be in-service only when unlocked.Additionally, or alternatively, administrator element 1250 may provide amechanism for a user to lock (e.g., by using a password) a route and/orNEs 250 associated with a route so that information associated with theroute cannot be deleted and/or edited by other users.

Circuit creation element 1260 may provide a mechanism (e.g., a button,an icon, a link, etc.) for a user to allocate a route based oninformation input using elements 1210-1250. Allocating a route usingcircuit creation element 1260 may cause network configurer 430 toprovide information input using elements 1210-1250 to NEs 250 forcapacity allocation based on the input information. Once a route hasbeen allocated, UIs 600-1100 may be updated based on the allocatedroute.

FIG. 13 is a diagram of an example process 1300 for receiving andstoring network configuration information. In some implementations, oneor more process blocks of FIG. 13 may be performed by one or morecomponents of NA 220 and/or user device 230.

Process 1300 may include receiving network configuration information(block 1310). For example, NCM 410 may receive the network configurationinformation from NPS 210 and/or NEs 250. NCM 410 may request the networkconfiguration information on a periodic basis (e.g., every second, everyminute, every hour, every day, every week, etc.). Additionally, oralternatively, NCM 410 may request the network configuration informationin response to a user request for a GUI that displays the networkconfiguration information. Additionally, or alternatively, NPS 210and/or NEs 250 may automatically provide the network configurationinformation to NCM 410 (e.g., on a periodic basis and/or when aconfiguration is changed).

Process 1300 may include storing network configuration information(block 1320). For example, NCM 410 may store the network configurationinformation in a memory associated with NA 220 and/or user device 230.For example, NCM 410 may store information associated with NEs 250,components of NEs 250 (e.g., FRMs), optical links (e.g., super-channelsand associated super-channel types) between NEs 250 and/or FRMs,allocation statuses of optical links, alert information associated withNEs 250, FRMs, and/or super-channels, etc.

FIG. 14 is a diagram of an example process 1400 for allocating bandwidthon network entities via a user interface. In some implementations, oneor more process blocks of FIG. 14 may be performed by one or morecomponents of NA 220 and/or user device 230.

Process 1400 may include receiving a request for a GUI that displaysinformation associated with one or more network entities (block 1410).For example, GUI manager 420 may receive a request from user device 230for a GUI. The request may be generated based on a user selection ofinformation that identifies one or more NEs 250 and/or one or moreroutes between NEs 250. In some implementations, GUI manager 420 mayauthenticate the user (e.g., using a user name and/or a password) priorto providing the requested GUI. The authentication may dictate whetherthe requested GUI is provided and/or the information that is provided inthe requested GUI. For example, based on the authentication of aparticular user, a GUI may be formed that includes only particularnodes, only particular types of nodes, only particular super-channels,only particular types of super-channels, etc. Thus, the informationprovided on the GUI may be based on the authentication of the user.

Process 1400 may include providing a GUI using stored networkconfiguration information associated with the network entities (block1420). For example, GUI manager 420 may provide a GUI to user device 230based on network configuration information stored by NCM 410. The GUImay display a representation of one or more NEs 250 based on a userselection of information that identifies the NEs 250. The GUI maydisplay optical links between the NEs 250, an allocation status of theoptical links, and/or other information described in connection with UIs600-1200. When information and/or a configuration associated with NEs250 changes, the GUI may be updated to display real-time informationassociated with NEs 250.

Process 1400 may include receiving, via the GUI, a user selection of anoptical link for bandwidth allocation (block 1430). For example, theuser may select an available optical link (e.g., a super-channel), andthe user may indicate a desire to allocate bandwidth on the selectedoptical link. In some implementations, the user may select an opticallink type (e.g., a super-channel type) to aid in selecting an availableoptical link for bandwidth allocation. GUI manager 420 and/or networkconfigurer 430 may receive the user selection of the optical link.

Process 1400 may include providing the selected bandwidth allocation tonetwork entities associated with the selected optical link (block 1440).In some implementations, network configurer 430 may provide theallocation information to NEs 250 associated with the user-selectedoptical link. Network configurer 430 may instruct the NEs 250 toallocate bandwidth according to a user selection.

Process 1400 may include receiving allocation verifications from thenetwork entities (block 1450). For example, NEs 250 may provide, tonetwork configuration manager 410, information verifying that NEs 250have allocated bandwidth based on the user selection. In someimplementations, process 1400 may return to block 1420. For example,network configuration manager 410 may provide GUI manager 420 with theverification information. GUI manager 420 may update the GUI displayedon user device 230 based on the verification information. For example,GUI manager 420 may update the GUI to display an updated allocationstatus of the optical links between NEs 250 based on the user selectionof the optical links for bandwidth allocation.

FIG. 15 is a diagram of an example process 1500 for recommendingallocations of bandwidth on network entities 250 in a manner to reducethe occurrence of fragmentation within the optical network. To reducefragmentation, the network configuration manager 410 utilizes one ormore fragmentation heuristics to provide an allocation recommendation,which if accepted by the user, will set up a route having a spectrumthat is preferably contiguous with the spectrum of other routes that arealready in use, but will be terminated separately. In one embodiment,the fragmentation heuristic analyzes the network configurationinformation discussed above to determine a channel that can implementthe route, but that has one or more spans outside of the route that arealready in use.

The process 1500 can be executed by the network configuration manager410, the GUI manager 420, and the network configurer 430 workingtogether and communicating with the user via a series of graphical userinterfaces that will be described in more detail below. In someimplementations, one or more process blocks of FIG. 15 may be performedby one or more components of NA 220 and/or user device 230.

By way of example, the process 1500 will be described as occurring whenthe optical network is provided with the configuration depicted in FIG.11. The process 1500 typically begins when a user receives a set uprequest for an optically engineered light path between a source entityof the network entities 250 and the destination entity of the networkentities 250. In this example, the set up request specifies the networkentity 250-2 as the source entity and the network entity 250-3 as thedestination entity. The optically engineered lightpath is a path betweena source entity, e.g., network entity 250-2 and a destination entity,e.g., network entity 250-3 via one or more other NEs 250 (not shown)such that the optical signal injected at the source network entity 250-2reaches the destination network entity 250-3 with a signal quality thatthe digital data can be retrieved intact. Such an optically engineeredlightpath is dependent on optical impairments encountered along thepath.

To process the set up request, the user then manipulates the NA 220,and/or the user device 230 to provide a request for a recommendation GUI1600, an example of which is shown in FIG. 16. The NA 220 and/or theuser device 230 receives the request for the recommendation GUI 1600 asindicated by a block 1510. In response thereto, the NA 220 and/or theuser device 230 provides the recommendation GUI 1600 to the user via theNA 220 and/or the user device 230 as indicated by a block 1520. The userfills out the recommendation GUI 1600 with information identifying thesource entity and the destination entity. More particularly, as shown inFIG. 16, the recommendation GUI 1600 is provided with a sourceidentifier element 1620 adapted to receive information identifying thesource entity 250-2 within the set up request, a destination identifierelement 1620 adapted to receive information identifying the destinationentity 250-3 within the set up request, and a mechanism 1630 (e.g., abutton, an icon, a text box, a link, etc.) adapted to provide theinformation identifying the source entity 250-2 and the destinationentity 250-3 to the network configuration manager 410 as indicated byblock 1530 and FIG. 15. In response to receiving the informationidentifying the source entity 250-2 and the destination entity 250-3,the network configuration manager 410 computes a route within theoptical network as indicated by a block 1540 along optically engineeredlightpaths by taking into consideration available resources and NEs 250,as well as optical impairments of all network entities along the route.

The network configuration manager 410 can use a variety of differenttypes of operations to compute the route such as a route based upon aleast cost to the network to provide the route. In this example, theroute is computed as span 1110 that is depicted in FIG. 11. Dependingupon the relative locations in the optical network of the source entityand the destination entity, the route may encompass one or more spans.

The network configuration manager 410 then determines all availablechannels which are configurable to provide the route as indicated by ablock 1550. This can be accomplished by analyzing the networkconfiguration information discussed above, that has been updated withthe real-time network deployment information. In the example depicted inFIG. 11, channels 4, 5, 6, 7 and 10 have an operational status ofavailable and may be configured to provide the route. For all availablechannels, as shown by block 1560, the network configuration manager 410determines the extent and span of such channels to determine whether ornot the channels have spans within the route, as well as spans outside(i.e., mutually exclusive with) the route. In this case, the channels 4,5, 6, 7 and 10 encompass the network entities 250-1, 250-2 and 250-3, aswell as spans 1110 and 1120. Then, as indicated by decision block 1570,the network configuration manager 410 determines whether the span(s)outside of the route have an allocation status that would indicate thatsuch span in unavailable. In this case, channel 4 is being used in span1120, while channels 5, 6, 7 and 10 are available in span 1120. The step1570 is preferably repeated for each available channel from step 1550 todetermine in how many spans a channel is unavailable. To reducefragmentation, the network configuration manager 410 will determine andprovide an allocation recommendation 1710 (FIG. 17) as indicated by ablock 1580 giving preference to allocating the channel(s) that havespans outside of the route that are unavailable, e.g., in this casechannel 4. Preferably, the allocation recommendation 1710 will givepreference to allocating channel(s) that have the most unavailable spansoutside the route. For example, if a first channel has two unavailablespans outside the route, then such first channel will be preferred overa second channel having only one unavailable span outside of the route.Exemplary allocation status that indicate that the space is unavailableinclude assigned, used, and blocked. The allocation recommendation 1710can be provided in the user interface in any suitable fashion to notifythe user. For example, the allocation recommendation 1710 can beprovided as a box as shown in FIG. 17, a colored area different from thetext identifying the recommended channel, a tag, flashingcomputer-generated icon, or the like.

FIG. 17 is a diagram of the example user interface of FIG. 11 generatedby the GUI manager 420 having the allocation recommendation 1710identifying channel 4 for allocation to the optical path to fulfill thesetup request. In the example shown, the allocation recommendation 1710is a visual representation within the user interface that may aid theuser in selecting an appropriate channel to reduce the occurrence offragmentation. As shown in FIG. 17, channel 4 is also configured tocarry optical signals between the network entities 250-1 and 250-2across the span 1120, but is terminated and separate from the opticalroute identified by the allocation recommendation 1710.

Once the allocation recommendation 1710 is provided on the userinterface, the user may select the allocation recommendation 1710 asindicated by a block 1590 to allocate the recommended channel, i.e.,channel 4 to the optical path as discussed below with reference to FIG.18. If during the block 1570, the system determines that none of thechannels have an allocation status of unavailable, then the process 1500branches to a block 1592 where one of the available channels isrecommended.

FIG. 18 is a diagram of an example user interface 1800 (“UI 1800”) thatmay aid a user in allocating optical network capacity by providingappropriate information to the network configurer 430 that is shown byway of example in FIG. 4 and described above. In some implementations,UI 1800 may be displayed by NA 220 and/or user device 230. Asillustrated, UI 1800 may include a source identifier element 1810identifying the source entity 250-2 that was recommended by the networkconfiguration manager 410, a destination identifier element 1820identifying the destination element 250-3 that was recommended by thenetwork configuration manager 410, a route information element 1830, aroute identifier element 1840, an administrator element 1850, and acircuit creation element 1860. Additionally, or alternatively, UI 1800may include fewer elements, additional elements, different elements, ordifferently arranged elements than those illustrated in FIG. 18.

Source identifier element 1810 may provide a mechanism (e.g., a button,an icon, a text box, a link, etc.) for a user to select a source for anoptical data transmission. For example, source identifier element 1810may identify an NE 250 and/or a component of NE 250 (e.g., an FRM) as asource for a data transmission that is to be transmitted over asuper-channel. In some implementations, source identifier element 1810may be populated based on user selection of one or more elements of UIs600-1100. For example, a user may select NE 250-2 on node displayelement 605 and/or may select FRM 1-A-5 on component display element 610to populate source identifier element 1810 with a node identifier and/oran endpoint identifier, as illustrated.

Destination identifier element 1820 may provide a mechanism (e.g., abutton, an icon, a text box, a link, etc.) for a user to select adestination for an optical data. For example, destination identifierelement 1820 may identify an NE 250 and/or a component of NE 250 (e.g.,an FRM) as a destination for a data transmission that is to betransmitted over a super-channel. In some implementations, destinationidentifier element 1820 may be populated based on user selection of oneor more elements of UIs 600-1100. For example, a user may select NE250-3 on node display element 605 and/or may select FRM 1-A-5 oncomponent display element 610 to populate destination identifier element1820 with a node identifier and/or an endpoint identifier, asillustrated.

Route information element 1830 may provide a mechanism (e.g., a button,an icon, a text box, a link, etc.) for a user to select routeinformation for an optical transmission to be allocated. For example, auser may select a rate of a super-channel to be allocated, a modulationformat of a super-channel to be allocated, a super-channel type of asuper-channel to be allocated, a super-channel identifier of asuper-channel to be allocated, a spectral slice identifier of one ormore spectral slices to be allocated. In some implementations, routeinformation element 1830 may be populated based on user selection of oneor more elements of UIs 600-1100. For example, a user may select asuper-channel rate, modulation format, and/or type (e.g., “500-xPSK”), asuper-channel identifier (e.g., “SCH 6”), one or more spectral slices(e.g., “slices 101-120”), and/or an OEL (e.g., “OEL-101”) on an elementof UIs 600-1100 (e.g., elements 615-635) to populate route informationelement 1830.

In some implementations, elements 1810-1830 may be populated by userselection of the allocation recommendation 1710 shown in FIG. 17.Selection of the allocation recommendation 1710 may provide elements1810-1830 with information associated with a source and/or destinationnode and/or endpoint associated with the selected super-channel; abandwidth, modulation format, and/or super-channel type associated withthe selected super-channel; a super-channel identifier associated withthe selected super-channel; and/or any other information associated withthe selected super-channel (e.g., information that may be used toallocate the selected super-channel).

Additionally, or alternatively, elements 1810-1830 may be populated byuser selection of an available cross-connect (e.g., termination point)displayed by TPDE 650. Selection of an available cross-connect mayprovide elements 1810-1830 with information associated with a nodeand/or endpoint (e.g., a source node and/or endpoint) associated withthe selected cross-connect; a bandwidth, modulation format, and/orsuper-channel type associated with the selected cross-connect; asuper-channel associated with the selected cross-connect; asuper-channel identifier associated with the selected cross-connect; asecond cross-connect associated with the selected cross-connect; a nodeand/or endpoint associated with the second cross-connect (e.g., adestination node and/or endpoint); and/or any other informationassociated with the selected cross-connect (e.g., information that maybe used to allocate the selected cross-connect and/or a super-channelassociated with the selected cross-connect).

Route identifier element 1840 may provide a mechanism (e.g., a button,an icon, a text box, a link, etc.) for a user to input information thatidentifies the route and/or optical lightpath specified by elements1810-1830. For example, a user may input a circuit identifier and/or alabel for the route to be allocated.

Administrator element 1850 may provide a mechanism (e.g., a button, anicon, a text box, a link, etc.) for a user to change an administrativestate of a particular route and/or NEs 250 associated with a particularroute. An administrative state may include locked or unlocked. A lockedadministrative state may take NE 250 out of service, and may allow auser to change a configuration and/or a parameter associated with NE250. An unlocked administrative state may prevent a user from changingone or more parameters and/or configurations associated with NE 250. Insome implementations, NE 250 may be in-service only when unlocked.Additionally, or alternatively, administrator element 1850 may provide amechanism for a user to lock (e.g., by using a password) a route and/orNEs 250 associated with a route so that information associated with theroute cannot be deleted and/or edited by other users.

Circuit creation element 1860 may provide a mechanism (e.g., a button,an icon, a link, etc.) for a user to allocate a route based oninformation input using elements 1810-1850. Allocating a route usingcircuit creation element 1860 may cause network configurer 430 toprovide information input using elements 1810-1850 to NEs 250 forcapacity allocation based on the input information. Once a route hasbeen allocated, UIs 600-1100 may be updated based on the allocatedroute.

Implementations described herein may assist a user in allocating opticalnetwork capacity. This may be achieved by providing informationassociated with an optical network configuration on a user device andreceiving changes to the network configuration (e.g., allocation ofcapacity) from a user interacting with the user device (e.g., via a userinterface).

The foregoing disclosure provides illustration and description, but isnot intended to be exhaustive or to limit the embodiments to the preciseform disclosed. Modifications and variations are possible in light ofthe above disclosure or may be acquired from practice of theembodiments.

Certain implementations are described herein with reference tosuper-channels. However, implementations described herein may be appliedto any optical links between network nodes, such as channels,super-channel, spectral slices, fibers, and/or any other optical datatransmission link.

While series of blocks have been described with regard to FIGS. 13 and14, the order of the blocks may be modified in some implementations.Further, non-dependent blocks may be performed in parallel.

Certain user interfaces have been described with regard to FIGS. 6-12and 16-18. In some implementations, the user interfaces may becustomizable by a device. Additionally, or alternatively, the userinterfaces may be pre-configured to a standard configuration, a specificconfiguration based on a type of device on which the user interfaces aredisplayed, or a set of configurations based on capabilities and/orspecifications associated with a device on which the user interfaces aredisplayed.

As used herein, the term “component” is intended to be broadly construedas hardware, firmware, or a combination of hardware and software.

It will be apparent that systems and methods, as described above, may beimplemented in many different forms of software, firmware, and hardwarein the implementations illustrated in the figures. The actual softwarecode or specialized control hardware used to implement these systems andmethods is not limiting of the implementations. Thus, the operation andbehavior of the systems and methods were described without reference tothe specific software code—it being understood that software and controlhardware can be designed to implement the systems and methods based onthe description herein.

Even though particular combinations of features are recited in theclaims and/or disclosed in the specification, these combinations are notintended to limit the disclosure of possible implementations. In fact,many of these features may be combined in ways not specifically recitedin the claims and/or disclosed in the specification. Although eachdependent claim listed below may directly depend on only one claim, thedisclosure of possible implementations includes each dependent claim incombination with every other claim in the claim set.

No element, act, or instruction used herein should be construed ascritical or essential unless explicitly described as such. Also, as usedherein, the article “a” is intended to include one or more items. Whereonly one item is intended, the term “one” or similar language is used.Further, the phrase “based on” is intended to mean “based, at least inpart, on” unless explicitly stated otherwise.

What is claimed is:
 1. A computer-readable medium, comprising: anon-transitory memory device storing one or more instructions that, whenexecuted by one or more processors, cause the one or more processors to:provide via at least one of an output component and a communicationinterface, a user interface that displays a representation of an opticalnetwork having at least three network entities and at least two opticallinks configured to carry optical signals in a first channel and asecond channel across at least a first span and a second span betweenthe at least three network entities, the first channel having a firstallocation status of available on the first span, and a secondallocation status of at least one of unavailable, assigned and blockedon the second span, the second channel having a third allocation statusof available on the first span and a fourth allocation status ofavailable on the second span; receive, via an input component, userinput regarding a setup request for an optical path between a sourceentity of the network entities and a destination entity of the networkentities, the optical path encompassing the first span and mutuallyexclusive to the second span; and provide, via the at least one of theoutput component and the communication interface, a visualrepresentation within the user interface of an allocation recommendationidentifying the first channel of the first span, based on the user inputregarding the setup request, the first allocation status, the secondallocation status and the third allocation status.
 2. Thecomputer-readable medium of claim 1, and further comprising: one or moreinstructions that, when executed by the one or more processors, causethe one or more processors to allocate the first channel of the firstspan to the optical path.
 3. The computer-readable medium of claim 1,wherein the user input is a first user input and further comprising: oneor more instructions that, when executed by the one or more processors,cause the one or more processors to allocate the first channel of thefirst span to the optical path based on second user input.
 4. Thecomputer-readable medium of claim 1, wherein the first channel is asuper-channel including a plurality of optical carriers, each of theplurality of optical carriers being associated with a particular opticalwavelength, the super-channel being provisioned in the optical networkas one optical channel.
 5. The computer-readable medium of claim 1,wherein the one or more instructions include a fragmentation heuristicthat when executed by the one or more processors analyzes the user inputregarding the setup request and network configuration data to generatethe allocation recommendation.
 6. A computer-readable medium,comprising: instructions that, when executed by one or more processors,cause the one or more processors to: receive, via at least one of aninput component and a communication interface, a setup request for anoptical path between a source entity of network entities in an opticalnetwork and a destination entity of the network entities, identify afirst channel and a second channel having one or more contiguous firstspan with an allocation status of available and being configurable toprovide the optical path between the source entity and the destinationentity; analyze network configuration data indicative of the firstchannel and the second channel with a fragmentation heuristic togenerate an allocation recommendation recommending the first channel tobe allocated to the optical path; and provide, via an output component,the allocation recommendation identifying the first channel forallocation to the optical path.
 7. The computer-readable medium of claim6, wherein the allocation status is a first allocation status, andwherein the instructions, when executed by the one or more processorscause the one or more processors to determine that the first channel hasone or more second spans, mutually exclusive of the one or morecontiguous first span, with a second allocation status of unavailable,and wherein the instructions further cause the one or more processors toaccess a network status database storing information indicative of anallocation status of the network entities and spans within the opticalnetwork.
 8. The computer readable medium of claim 6, wherein theinstructions, when executed by the one or more processors cause the oneor more processors to: receive, via the input component, user input toallocate the first channel to the optical path, and pass signals via thecommunication interface to allocate the first channel to the opticalpath based on the user input.
 9. The computer-readable medium of claim6, wherein the instructions that cause the one or more processors toprovide the allocation recommendation are defined further asinstructions that cause the one or more processors to provide a visualrepresentation of the allocation recommendation in a graphical userinterface.
 10. The computer-readable medium of claim 6, wherein theallocation status is a first allocation status, and wherein thefragmentation heuristic causes the one or more processors to determinethat the first channel has one or more second spans, mutually exclusiveof the one or more contiguous first span, with a second allocationstatus of unavailable to generate the allocation recommendation.
 11. Thecomputer-readable medium of claim 6, wherein the first channel is asuper-channel including a plurality of optical carriers, each of theplurality of optical carriers being associated with a particular opticalwavelength, the super-channel being provisioned in the optical networkas one optical channel.
 12. A method, comprising: receiving, via atleast one of an input component and a communication interface, a setuprequest for an optical path between a source entity of network entitiesin an optical network and a destination entity of the network entities,identifying a first super-channel and a second super-channel having oneor more contiguous first span with an allocation status of available andbeing configurable to provide the optical path between the source entityand the destination entity; analyzing network configuration dataindicative of the first super-channel and the second super-channel witha fragmentation heuristic to generate an allocation recommendationrecommending the first super-channel to be allocated to the opticalpath; providing, via an output component, the allocation recommendationidentifying the first channel for allocation to the optical path; andpassing signals via the communication interface to allocate the firstsuper-channel to the optical path.
 13. The method of claim 12, whereinthe allocation status is a first allocation status, and wherein themethod comprises determining that the first super-channel has one ormore second spans, mutually exclusive of the one or more contiguousfirst span, with a second allocation status of unavailable, andaccessing a network status database storing information indicative of anallocation status of the network entities and spans within the opticalnetwork.
 14. The method of claim 12, further comprising: receiving, viathe input component, user input to allocate the first super-channel tothe optical path, and wherein passing signals is defined further aspassing signals via the communication interface to allocate the firstsuper-channel to the optical path based on the user input.
 15. Themethod of claim 12, wherein providing the allocation recommendation isdefined further as providing a visual representation of the allocationrecommendation in a graphical user interface.
 16. The method of claim12, wherein the allocation status is a first allocation status, andwherein the fragmentation heuristic causes one or more processors todetermine that the first super-channel has one or more second spans,mutually exclusive of the one or more contiguous first span, with asecond allocation status of unavailable to generate the allocationrecommendation.